Internet Explorer End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Internet Explorer versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Internet Explorer 11 Embedded is supported until October 14, 2031, its end-of-support date. The next Internet Explorer version to reach end of life is 11 LTSB, on October 14, 2031. 5 of 9 tracked Internet Explorer versions are past end of life; the most recent to reach it, 7, did so on October 10, 2023. The full Internet Explorer lifecycle, with every version's release and end-of-support date, is in the table below.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7 | — | Oct 18, 2006 | Oct 10, 2023 | 1079 days past EOL | EOL |
| 8 | — | Jun 17, 2009 | Jan 12, 2016 | 3907 days past EOL | EOL |
| 9 | — | Mar 15, 2011 | Jan 12, 2016 | 3907 days past EOL | EOL |
| 10 | — | Oct 30, 2012 | Jan 31, 2020 | 2427 days past EOL | EOL |
| 11 Embedded | — | Nov 13, 2013 | Oct 14, 2031 | 1847 days remaining | Active |
| 11 Server | — | Nov 13, 2013 | Oct 14, 2031 | 1847 days remaining | Active |
| 11 LTSC | — | Nov 13, 2013 | Oct 14, 2031 | 1847 days remaining | Active |
| 11 LTSB | — | Nov 13, 2013 | Oct 14, 2031 | 1847 days remaining | Active |
| 11 | — | Nov 13, 2013 | Jun 15, 2022 | 1561 days past EOL | EOL |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/internet-explorer)
Internet Explorer release and support pattern
Of the 9 release lines tracked, 5 are past end of life and 4 are still within support. The newest line, 11, was released November 13, 2013. The next scheduled end of life is 11-ltsb on October 14, 2031 — 1846 days from this build. The longest-supported line currently published is 11-embedded, to October 14, 2031.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Internet Explorer security intelligence
CISA KEV history: Internet Explorer is named in CISA's Known Exploited Vulnerabilities catalog 40 times, most recently on 2026-05-20, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does Internet Explorer end of life mean for your organization?
When a version of Internet Explorer reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Internet Explorer should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Internet Explorer reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Commercial extended support | Not available for Internet Explorer from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →